Once the process and governance for any variance to agreed plans for the Support WIP and tickets in scope projects is finalized, the WIP Lead must confirm with Run organization, which team should work on those tickets which Capgemini has to take over. Roles and responsibilities have to be appropriately assigned and a detailed Responsibility Matrix For Support WIP must be created in alignment with all the relevant stakeholders. The WIP Lead must identify dependencies on Client, third party and other stakeholder and ensure this is clearly stated in the Responsibility Matrix For Support WIP and agreed by all stakeholders.

A take-on plan must be created for taking over the Support related WIP and tickets.

Typically the categorization is done as:

·      Support WIP and tickets which Capgemini must take over

·      Support WIP and tickets that other relevant service provider(s) should take over

·      Support WIP and tickets which the Client or incumbent should complete.

Support WIP and tickets categorization may change as transition progresses. If this does occur, then changes must be agreed with all stakeholders.

Support WIP Inventory must be created with all of the relevant information gathered and updated regularly to help track and report.